ProTALK network proposal, file number #2. The nation wide message system
This proposal is based on the idea that certain boards want to network
certain message bases. This proposal assumes that the process of packing
messages since the last sent counter and skipping those received from foreign
systems is worked out and prepared.
Terms:
Conference:Echo mail conference having a subject number from 1-20 or more.
Message base: A local message base existing on any board
Host system: The system that recieves the call
Low-level, base, bottom end systen: A system that only calls out.
For this network, we will be using three different sets of code. One will
be for the bottom end network site, where it will just call out and not recieve
calls. The second set of code will be involved in the both sending and
recieving of calls. The third set, much like the second will be the master
file servers code, for The Apple Rebel BBS ONLY!.
Two different files are kept on the second level or host system. One of these files will be a list of conferences that the board below it wants in ther
message base. The filename for this file will consist of the three letter
extension and "REQUEST". For a list of conferences that the board GEN wants when they are connected it would be named "GEN.REQUEST". The file would contain a simple list of numbers of the conferences to be networked.
The second file and the most important one is a file that will contain when the last conference file from a particular system was sent. Called "GEN.LASTSENT" with GEN replacing the three letter extension. The file will be a list of files that were sent last from the host system to the low level system. This is in order to not allow duplicate files to occur on the low level system. The file would look something like this:
SDE01.071688
TEM02.071588
In other words, if the file name of this file was GEN.LASTSENT the last packed conference 01 file from SDE would be the one on 071688 or July 16th 1988. More about this file later.
On each system, more importantly the host systems there will be 20 or more directories set up within the B: or G: directories (depending on the TOTAL number of conferences that are being networked system wide). When a low level system is uploading conference files the host system will sort them into the conference numbers directories by first recieving the conference number of the following conference file and then recieving the file there.
The uploading is the simple part, since the updating is done on the low level system. When it comes to the low level system downloading the requested conferences, it goes through much the same process, BUT the host system will check that magical XXX.LASTSENT file against the file name of the file in the directory. If the file in the directory is newer than the one last sent it will send it, first by proceeding the file with the conference number of the file being sent. If the file in the directory is the same, or lower (can't happen) it will not send it.
This allows conference files to exist on one system while allows many low level systems below it to call and download these files at their own time and frequency.
When it comes to using the master file server, The Apple Rebel BBS, it is likely that all the boards beneath the master file server will be networking nearly all the conferences. So therefore the files say TEM.REQUEST will be one containing a large set of conference numbers.
This system allows for faults and features to creep in to the network. Imagine a network consisting of five boards for example.. here is a tree diagram to understand it.
APR - The Apple Rebel BBS
/ \
/ \
Temple of Karnak TEM \
/ \ \
/ \ \
GEN SDE FLV
If both GEN and SDE want to recieve conference number 4 on their systems and TEM is NOT recieving the files from APR it will still allow for SDE and GEN and TEM to share the conference, or even if TEM is not conferencing it. But because TEM has not requested conference number 4 from APR it will not recieve it so messages posted on FLV in echo conference number 4 will not appear on TEM, GEN or SDE.
On each system there will be some form of cross reference list, it will contain a list of the conference numbers and their corresponding board numbers on the local system.
During each transfer of conference files there must be a batch file kept containing all the files recieved that must be unpacked to the local message base system. This applies to ALL boards. The check would involve checking the conference number of the message file recieved against the list of conferences that the local board is networking. After transfer this list is taken and the messages unpacked to the local system.
Is this comprehendable? There are a couple things that can be improved on. If you can think of a way to combine things and make everything quicker, please tell me.
Setting up a link between two boards should be relatively easy. I.E. if a new board wants to join the network the two sysops must get together and discuss these points.
1) The new system MUST net.config and select his local message base numbers and identify which conference numbers these refer to while creating the cross reference file spoken about earlier.
2) Inform the host system sysop as to the conference numbers he wants to network therefore creating the XXX.REQUEST file.
3) Create the XXX.LASTSENT file by setting a arbitrary date for the records.
4) The new system must create the specified directories.
5) The password and time for networking must be decided upon, and then the schedule.
Setting up a host system will be a little difficult. But if it is already a network site, it makes it slightly easier.
matthew
Ram Chip
A true canadian.
Contact me on Generic -user-#1, or The Apple Rebel BBS -user-#144.
